My hypothesis is that something in the Grails deployment is deliberately reconfiguring logging (i.e. turning it off). We've got a per-deployment log isolation feature in upstream right now that would be quite suitable for this situation if I'm right.