This is a clear misuse of the JMS message subsystem. Rethink your overall design !
Oh I forgot to say, "Legacy App."
So if I were willing to add new code, I'd consume those messages in the MDB then store them in another queue which nobody is consuming. But the queue doesn't finish in time only when there are other problems, so I prefer a n administration solution over a programmatic one.
I think you might need to write an external program to re-write some of the message data. It itself contains the destination name. I recommend you write an MDB, on maybe another JBoss server, that runs once a night and does the rewriting, then exits.