Add basic Rails4 integration test (TORQUE-1115)
Try to be a bit more robust at handling JMX errors when restarting runtimes during integs
More upping of receive timeouts for integs
Log runtime destroying as well as creation
Wrap the runtime restart scanner in a try/catch block (TORQUE-819)

This is just to ensure the scanner doesn't die if an error happens
during a scan.
Fix some runtime memory leaks exposed by the zero-downtime deployments (TORQUE-819)

Once zero-downtime deployments added restarting of services, it
exposed a couple of places where we could hold onto Ruby objects from
previous service runtimes.

This also fixing a potential leak in the SharedPool restart
implementation that could result from restarting the pool multiple
times before the runtime from the first restart gets retired.
Remove another potential runtime memory leak from zero-downtime implementation (TORQUE-819)