Apparently, Hibernate tries to register a work on a transaction that is no longer active. But to me the latest code cannot fall into this case. Plus the user solve his issue by increasing the heap size. Could it be that JBoss keep track of the transaction or something related to the Tx in some kind of weak hashmap making it candidate for GC when memory is low. This could explain the behavior the user have.