I can confirm that 4.3.1.Final still contains this bug. Is there a timeline for this bug to be fixed, given that there are already 2 issues opened against this issue, both of which contain proposed fixes?