I have the same ssis pachage pattern. like one master sequence which calls four other sequences packages, those sequences have chiled pakages.

I have not got into this issue yet because i use mostly stored procedures in the packages and data is also small amount as of now, but it is going to increase like in 100000s or more.. I hope it doesnt get stuck in that case.

May be you can try using stored procs instead of different transformations.