Multiple RuntimeEngines not getting disposed

Multiple RuntimeEngines are not disposed properly when created in the same Transaction. When a RuntimeEngine is created there is a transaction synchronization (DisposeSessionTransactionSynchronization) created to dipose it after the transaction commits. All instances of DisposeSessionTransactionSynchronization are identical according to their compareTo method, which is what the TransactionSynchronizationContainer uses when storing them. So only one synchronization gets stored and when the transaction commits there are stale runtime engines present.