Don't lose transient changes in a multi-transaction JCA setup

When JCA is used, and several successive calls to DocumentManagerBean are done in different transaction, the low-level SQL SessionImpl actually returned from the pool may be different each time.
This means that the unsaved changes made by the first call may be invisible to the second call if it executes with a different underlying SessionImpl.