Brett Meyer forgive me if I'm mistaken, but this bug is specifically for the 4.2.x series (JPA 2.0). It's still affecting 4.2.10.Final.

So it doesn't pertain to 4.3.x (JPA 2.1) and later.