I've successfully reproduced this situation with ehcache 2.4.3, so bug fix shouldn't wait ORM 5 release.