[TORQUE-1012] Eager loading for messaging is not working with ruby DSL and a shared pool

Fixes https://issues.jboss.org/browse/TORQUE-1012

Why in configure gem, the shared pool was stripped from other configuration options? Was it because shared pool is a special case and is... uhm, shared? If yes, does my commit fix the issue in the way you want to have it, or maybe we should explicitly allow to change the laziness of the shared runtime pool?