You could do the following:
(1) add JndiKernelRegistryPlugin bean to MC - this knows how to lookup jndi
(2) add @Depends("my-hibernate-session-jndi-name") to your service bean
This would create explicit dependency.
But one note, (1) is then used at every MC lookup call, hence performance penalty
+ MC could find some other njdi entries you might not wanna expose (you could create your own version of JKRP, which would "fix" this).