Summary
	* Issue title: Repository removing failed because repository in use when forceRemove is true 
	* CCP Issue:  N/A
	* Product Jira Issue: JCR-1943.
	* Complexity: Medium

Proposal
 
Problem description

What is the problem to fix?
	* Repository removing failed because repository in use when forceRemove is true 

Fix description

Problem analysis
	* Between clossing alive sessions and removing repository there is a bit of time when new sessions can be opened.

How is the problem fixed?
	* Remove repository despite of existance alive sessions.

Tests to perform

Reproduction test
	* Only reproduce in could workspace

Tests performed at DevLevel
	* Functional testing

Tests performed at Support Level
	* N/A

Tests performed at QA
	* N/A

Changes in Test Referential

Changes in SNIFF/FUNC/REG tests
	* No

Changes in Selenium scripts 
	* No

Documentation changes

Documentation (User/Admin/Dev/Ref) changes:
	* No

Configuration changes

Configuration changes:

    No

Will previous configuration continue to work?
	* Yes

Risks and impacts

Can this bug fix have any side effects on current client projects?
	* Any change in API (name, signature, annotation of a class/method)?: N/A 
	* Data (template, node type) migration/upgrade: No 

Is there a performance risk/cost?
	* No

Validation (PM/Support/QA)

PM Comment
	* Validated

Support Comment
	* Validated

QA Feedbacks
	* N/A

