Seems like this problem manifests itself only when using JTS.
JBoss JTS uses com.arjuna.ats.internal.jta.transaction.jts.TransactionImple as javax.transaction.Transaction implementation class and it's hashCode implemenation uses complex delegation chain for hash code calculation (which can lead to remote calls or attempt to call an object in cleaned-up state - exactly our case: com.arjuna.ats.internal.jts.orbspecific.Controlimple is in destroyed state)
But com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple hashCode() implementation ( which is used when JTS not enabled ) simply delegates to tx.get_uid().hashCode() and TransactionSycnhronizer works as expected.