I also discovered this "feature' last week and believe it is one of the major flaws with Flow.
A user creates Flows on behalf of the company, but is forced to pass thier connections through, instead of the connection running in the context of the user running the Flow.
This no doubt will cuase more issues as:
a) The users password, who created the Flow is changed
b) The user creating the Flow leaves the company
ETC.
So I suppose we have to look at some form of Service Account to get arround this problem