I would look at writing a workflow and a custom step. Then query pages under an AEM path. Delete those that meet the name pattern. 

I agree - update to the latest OSGi standards.

Are you looking for LIB conflicts? This is very bad practice.

Too bad you are not using a more recent version of AEM. With coral-based multifield, they improved the functionality. You do not need ACS-Commons.

try deploying it via a package to the pub instance.

Working with Editable templates and client libs are covered in this doc:WKND Tutorial OverviewUsing LESS CSS and developing components in an editable template - you can design most sites to meet your customer requirements

Why did you post in Experience Manager forum?

IN AEM - you can basically write a custom log file for a given Java package (not a rep path). Creating a custom log file for an Adobe Experience Manager project

Your description makes no sense. Components do NOT have policies. An Editable template have policies that Define what components are allowed to be used within a page that is based on an editable template.Also please point to AEM documentation that describes what you refer to as an App Container. Thi...

Only way is to use Java API as Arun has referenced.