There's nothing wrong with this, its just a... uncommon and sometimes a lot of effort to get right.

Use SessionFactory.evict()

Evicting from current sessions would be incredibly evil, which was what this thread was about.

We had a similar issue within an MDB JMS implementation. We ended up using a ThreadLocal pattern to maintain open Sessions between each MDB onMessage() call and put in specific transaction handling code to make sure Level 1 caches were cleared on commit() or rollback(). Sessions are really only closed if the container kills the thread due to inactivity. Level 2 cache updates were an easy add on once the base Session handling was clean.