Gennady,
I’m assuming that you have your reusable orchestration in a separate assembly? If this is the case, when you use the StartOrchestration shape you will tying the orchestrations together through assembly references, so when you come to redeploy or delete the called orchestration you will receive the ‘already in use error’ that you are seeing, irrespective of which application the orch sits (don’t forget, the application is just a logical bucket for artifacts)
What you will need to do is re-develop the calling and called orchestration to use direct message box communication, thereby de-coupling the two orchestrations: the calling orch will send messages directly to the message box (rather than using the Start/Call Orchestration shape) and the called orch will listen for messages via a subscription. You can then re-deploy the called/reusable orchestration without any worry about dependancies.
I’ve really whipped through what you want to do here, so go and read the following two blog posts: http://geekswithblogs.net/cyoung/articles/19546.aspx and http://blogs.msdn.com/kevin_lam/archive/2006/04/25/583490.aspx
Cheers, Nick