Timeout Exception Test Case, Configurable Keeping/Removing in Replication, removing putReject() & version limit in StorageMemory

Pull request contains:
<ul>
<li>Test case for heavy load (lot of versions to replicate, nRoot approach). triggers timeout exceptions.</li>
<li>Added flag in replication, which indicates deleting or keeping of data, which is no more in replication range (responsibility) of replicating peer.</li>
<li>Removed putReject method. Instead usage of remove() is better.</li>
<li>StorageMemory has now a configurable version limit</li>
</ul>