This issue is very similar with HHH-5948 (same error), that apparently appeared in Hibernate 3.6 and is still reproducible as of Hibernate 4.2.8.Final (I ran again into it this week). I proposed a fix that I'm still using today.
Please check HHH-5948 : there's also a test case that you can use to reproduce this error.