What happens when Connection#close() is called and there is an active local JDBC transaction for non-JTA datasource connection in JBoss?

Issue

• What happens when Connection#close() is called and there's an active local JDBC transaction for non-JTA datasource in JBoss?
• We are using non-JTA datasource (setting jta="false" to <datasource>) and calling Connection#setAutoCommit(false) to disable auto-commit mode and use local JDBC transaction in our application. When our application call Connection#close() before calling Connection#commit() (or Connection#rollback()) by mistake, it looks the local JDBC transaction is still active in the another requst which uses the returned connection. For example, statement.executeQuery("select current_timestamp;") returns an old timestamp where the previous request start a local JDBC transaction.