Never heard something similar, but this most probably has nothing to do with JBoss per se, it looks like a problem of the Operating System. I.e. you have a process (the JVM) that consumes many resources in terms of CPU, Memory and File I/O (at least in the initial stages) and that somehow makes the systrem clock run faster? What JVM you are using?
We found the problem. It was a bug in JVM.
solution: add the JVM param '-XX:+ForceTimeHighResolution'