My wild guess would be that the time spent obtaining a connection from any brand of database connection pool will be dwarfed by practically every other operation in your application, so I'd be hard pressed to recommend one pool over another.
I have applications running on Weblogic and
Tomcat. I always use the container-managed database pool. My reasoning is that my application can focus on business problems rather than configuring the environment and setting up resources, and it's one less third-party dependency I have to manage.
In your situation, I would probably leave my existing applications as-is, but look at using container-managed pools for future applications.
