Not a bug.
This is determined by the site's configuration, not by the app.
We recommend (via our installation guide) the use of the deprecated AbandonedObjectPool (due to the use of removeAbandoned=true in the DBCP props). This is not a serious issue. The AbandonedObjectPool does work.
Based on my own experience, it also works around a bug in DBCP that causes lost connections / incorrect pool size accounting with certain drivers on certain database exceptions.
Site admins can avoid this simply by changing the DBCP configuration properties in the context xml file, setting the removeAbandoned=false or removing the settings for it and the removeAbandonedTimeout altogether.