ConcurrentLongHashMap and ConcurrentLongHashSet should avoid volatile set cost on put/remove

ConcurrentLongHashSet/HashMap are making use of unecessary volatile store of size/capacity for modifier methods. 

The current JVM implementation of volatile store for multicore x86 is making use of a StoreLoad barrier for this operation: the most expensive one.

These volatile stores could be replaced by plain stores/lazySet ones with no effects on the correctness of those methods.