This issue has been already captured at https://issues.jboss.org/browse/TEIID-1371 however it has not been fixed yet. If you want take look provide us a patch, you are certainly welcome. Right now other priority bugs/features have consuming our time.
Thanks for update. You said that there is a workaround for this problem.
The workaround is restarting the JBoss server after copying the new translator jar file?