I'm not sure this will work for the container -- at the time we reload locale information, we've not actually set the body classes yet, as that's waiting for the first call to render an enyo.object due to the changes made a couple of sprints ago to use the new enyo.dom.addtBodyClass.

However, in the usual case, the container will be loading with the same locale as the final app, it's just the string bundles we need to reload, so maybe this isn't an issue.  I could see a problem if the container was created in one locale, then got a localechange message while running but before launching the app.  Here, we would be modifying class tags that don't exist, while leaving the in-process class tags to be set on first render with the old locale info.

I'll add some better accessor methods to enyo.dom for this case and we can switch to that.