Reproduced the errors with JBoss undeploying beans but leaving them discoverable.

This was especially noticeable with JDBC pools.

Instead of closing the connection or failing all the items, log when this occurs, and keep track of the consecutive failures (for future use?)

If the MBean is available at a later date, the collections will resume seamlessly.
Merge pull request #13 from egineering-llc/issue_10

Fixes for stale JBoss beans.