We're using 4.1.9.Final and seeing the exact same problem. Is this a known issue for 4.1.9.Final?

Ideally if the bug is fixed in the latest version 4.3.6.Final we'd just upgrade to that, but there seem to be some compatibility issues between our version of Spring and the 4.3.6.Final version of Hibernate.