There could be times when you want to enter an orchestration through both a file drop as well as a web service call. The first obstacle you could encounter is that you can only have a single receive shape with 'Activate=True' and since we are not talking about convoys, multiple receive shapes in a sequence is certianly now the way to go. Thank you Heavens that MS provided the 'Listen' shape which allows you many activate-able receive locations. My wonderament start after the Listen shape where I have to replicate the same process for each entry point and the orchestration design looks pretty messy for even a simple task with parallel running flows essentially doing the same thing.
It might be conversely stated that flows are different since a request-response(Web Service) flow will be different from a request-only (File Drop), however I still wonder why Runtime cannot differentiate the flow based on the request type, eventually allowing me to define a single flow no matter how many entry points I have.