It appears as a JVM bug.
We have never noticed a similar issue before.
As the "scavenger" should be a part of the Garbage Collector, perhaps configuring a different GC algorithm could be a temporary workaround.