If you look at org.jboss.invocation.pooled.server.PooledInvoker,
JBoss does seem to cache the connection on the client side.
However the CurrentClientPoolSize is already 0 during my testing.
I used COMMIT D option and "optiond-refresh-rate".
Originally I thought JBoss would automcatically RELOAD the cache beans after the "optiond-refresh-rate". However it turned out JBoss just removed the cache, no RELOAD.