I am seeing similar behavior when invoking a remote EJ B. The max pool size is completely ignored.
The whole pooling mechanism was originally created to limit resources (i.e. limit concurrent access to services) and to reduce the overhead of construction. The current design of the ejb and mdb pools clearly fails at all of these. This behavior of pooling is really unexpected and also inefficient.
Can this be solved any time soon?
[Message sent by forum member 'erikengerd' (erik_at_brakkee.org)]
http://forums.java.net/jive/thread.jspa?messageID=372208