using c3p0 - each user has own database username and password and thus conn pool

[T. Gullo]

Any best practices for using c3p0 in an environment where each user has their own database username and password?

I know this sounds a bit odd, but certain environments like the one I'm in, require each user to have an Oracle username and password managed by the Oracle db.  I'm using c3p0 for connection pooling.  

One of the problems I've run into is changing of passwords.  If a user changes a password through the database, stale connections are still alive in the pool.  Even setting maxIdleTime and checkin connection don't seem to solve the problem.