Recovery manager service may not always use the correct orphan filters

I've been looking into certain transaction recovery use cases (with EJB remote beans involved) and while investigating the issues, I noticed that the orphan filters being set in the JTAEnvironmentBean might not be available to the Recovery manager service. That's because the MSC service which sets up the transaction recovery manager service runs before the JTAEnvironmentBean is setup with the orphan filters, which actually happens in a separate MSC service (Arjuna tx manager service) which starts after the recovery manager MSC service.

(Sorry, don't have the code in front of me, else would have added the exact class names - will do so later).