Bad state in second connection to same datasource in same TX

There's a case where, particularly if you're using XA, if you use a second connection to the same datasource in the same transaction, ManagedConnection will fetch the delegate transaction from the transaction registry, but the xaConnection and xaResource fields are dropped.