Just updated to 4.3.8.Final and the issue is still there (in exactly the same fashion).
The fix posted by Hepoi Ko seems to work perfectly for me, but I don't know what impacts it might have on the rest of the framework.