Hi Raghuram,
This may be reason that entire SICF is designed as a tree structure and every services / alias are under root node 'SICF' and there after the under particular sub node.
Its same for the web dynpro application , these are kept under service tree '/default_host/sap/bc/' .
So in that tree structure each one 'sap' / 'bc' are actually services same as your web dynpro application. That means the report which is creating services is taking reference from parent service and keeping it under the particular node & as mentioned by Kiran they can be accessed directly over the Internet via HTTP protocol so they are kept inactive.
There is no exception for custom ones because the are also services created under this service tree in the same way.
Regards,
Monishankar C
