There isn't a quick fix.
So to control the churn we'd have to comment out that property from collection
The config is in the collector/jboss-5.config, we can comment that out and make sure that churn is not in the way of the FMS performance.
Search for "fake attribute" in that config, there are two places where that comment is made about jndiName property, comment out those two lines and save the config...no appserver restart required.
This can be done on the fms so that all agents can get it...when looking up the config (Advanced configuration) make sure the correct version is chosen from the drop down that should match the version of the agent you have.