Defining application-scoped work manager in Plan.xml

I am having trouble getting my MDBs to recognize work managers that I have
defined in my deployment plan using the admin console.

The work managers show up properly when I click the deployed application and go
to the Deployments->myapp.ear->Configuration->Workload tab.  They do
not show up, however on the
Deployments->myapp.ear->Monitoring->Workload tab.

Also, when the server boots, I get a log message like this:

 [pre]<BEA-002919> <Unable to find a WorkManager with name
FaxErrorQueue. Dispatch policy FaxErrorQueue will map to the default WorkManager
for the application care360-backend-app-2008>[/pre]

even though FaxErrorQueue shows up under Configuration->Workload.

[b]BACKGROUND[/b]

I am upgrading an 8.1 wls to 10MP1.  Our MDBs are deployed as a single jar,
included in 2 separate ears, which are deployed to 2 separate clusters.  So, if
we have 2 clusters with 2 managed servers in each cluster, we deploy each MDB to
all 4 servers.  We control the Execute Queues for each server in 8.1 with
different values so that MDB#1 might have a single thread in one managed server
and zero execute threads on another.  Using the deployment plan is the only way
I can think of to implement this.  We would prefer not to use the 8.1 emulation,
as the deprecated execution queues will have to be dealt with eventually.  I am
open to any other approaches to accomplish this as well.

Thanks,