In some scenarios, Artifactory Garbage Collection might not delete candidates for deletion

In some scenarios, when the Artifactory Garbage Collection is triggered, it scan the artifacts which are candidates for deletions, but fail to delete these claiming that the binary are still being read. See the below log entry for example:
2016-02-02 09:00:00,033 [art-exec-1422714] [INFO ] (o.a.s.d.b.s.BinaryStoreImpl:717) - Binary ded0fc4a36995f4f0d11b2d3c455e27107f0d2fc is being read! Not deleting.