Ah now I understand, and thanks for the fix!

fixed in 5.2.9.32-SNAPSHOT, a release will follow later

It is only in 5.3.1, because this was the current release cycle at the time it was fixed.
At this time 5.2.9 already was a RC and it was not clear that it was a regression. If a cycle is in RC, it only gets regression and security fixes.
With the knowledge at the time there was no reason to backport that to 5.2.9.

It seem to be a regression, but not in 5.2.9, it is a regression in 5.2.8, so i think we can make a hotfix for 5.2.

I personally had this problem with 5.2.8.50 and heard someone else also with this problem on 5.2.8.50 and additionally with 5.2.9.31.

When I brought this issue up in the Lucee Slack on Aug 17th, I reported it as a problem in 5.2.8 and 5.2.9. I didn't realize this ticket was only fixing 5.3. I tagged both and in that Slack message.