Yes, maybe, that could be a good way to centralise all references to Component.getInstance (and the names), but note that it is still handy to have methods in the object (eg TranslationWorkspaceManagerImpl).  These methods can then be overridden easily for test-mocking purposes.

I think the ServiceLocator bean should be Application scope, not Stateless, so that we can keep to our new scoping rule: don't inject anything into an Application bean except other Application beans.

Also, the ServiceLocator bean might end up a bit of a monster (it is a service locator, after all...) with too many dependencies in and out.  Multiple locator beans could help here.