open the in-memory output stream immediately when scheduling it on the run loop
- if never opened (as was the case if no response was received) apparently calling close will not implicitly remove the stream from the runloop (apple docs are misleading?)
Merge pull request #2178 from jtomson/fix_outputstream_leak

Fix AFConnectionOperation outputStream leak if no response is received