Is it possible to configure & change MDB maximum pool size during run-time, after deployment?

Using JMX-console I saw that the MDB uses DestinationManager which uses BasicThreadPool and after changing it (using 'MaximumPoolSize' attribute) it affected on all MDB`s in the server, and I would like to avoid it.