Checking of transaction complete is NOT trapping threads that have been rolled back
but not removed from the transaction context of the thread.

e.g.
1) the transaction timed out and was rolled back
2) the user used the Transaction rather than TransactionManager api which did does not remove the thread association

In
org.jboss.ejb.plugins.AbstractTxInterceptorBMT
and
org.jboss.web.tomcat.service.jca.CachedConnectionValve

There needs to be extra code (after the incomplete check) that says that if the tx status is not NO_TRANSACTION
is does TransactionManager.suspend(transaction) to remove the thread assocation.