The container you're starting is in 'manual' mode, so as long as you only have one start/stop scenario pr TestClass, you don't have to stop it manually. Arquillian will automatically stop containers in manual mode in AfterClass to 'prepare' for next TestClass.
If you remove the @After it all works in 1.1.5.Final as well;
Now that is not per say the real issue here, as stopping manually a manual container should work just fine. Investigating..
The problem is @After is called before the Arquillian After lifecycle, not inside as it used to be. This came along with the rewrite to support Junit Rules better. Working on a fix.
Nice, thank you for the investigation.