WunderBoss.container should always return a new container from Ruby

The previous behavior of sometimes returning a new container or
sometimes reusing an existing container depending on the arguments
passed in was confusing and took me a while to track down why it was
causing some TorqBox spec failures.
Only tear down Ruby runtimes we create