Comment 1 for bug 797680

Oh, this is really obvious. The menu service is instantiated and started from chrome, as part of the overlay in to the main messenger window. This isn't loaded here, so the menu service never starts.

I can probably just add the menu loader service to the profile-after-change category in the chrome.manifest, so we won't rely on any chrome code to load it.