I went to check if the problem still existed ***PRIOR*** to attempting restart, and also to see which node(#29) I was on... the problem has RESOLVED on its OWN... to the best of my knowledge the DEV server was not bounced in the interim.
ls -la /jboss/jboss-eap-6.3/standalone/log/*bounce*
Turns out the DEV server *WAS* bounced in the interim (manually by one of our Developers)... our bounceflagfile only gets touched during the weekly cron-job auto-bounce and not when bounced manually. we are in the process of updating the manual bounce script to match the cron-job bounce script so that next time we can know the exact timestamp of the last bounce... Any idea about why an App Server bounce should help fix the remote tracer issue though? Bouncing is not something we want to do with any regularity in our higher environments.