Multiple database publishing destinations - resource issues?

We currently publish to two databases from our system - one for our preview website and one for publish/live. We’re considering adding another database publishing destination, for metrics and reporting use. Defining the new destination isn’t a problem, but we’re wondering what system resource constraints we might run into as we add additional JDBC datasources - this will bring the total to four - the repository, our current two publishing DBs, and the new one. Will they be competing for the use of the same set of connections, and thus will we run out? Do we need to change something about the JBOSS connection pool(s), or some other CMSystem/JBOSS configuration to prevent problems?

I’d be happy to hear about anyone’s experiences, or even speculation :-), about what problems might arise as we add database publishing destinations.