There is no error in the log when the connection gets reset. I have not removed either profile as of yet. I just captured the trace yesterday and was confused by the behavior of the client.
Most of the time the client waits for the BigIp to respond with 100-continue and then sends the SOAP request. Those transactions go through normally. So what I was unsure of was if the client was acting abnormally or if BigIp was not handling this properly.
I have not disabled either the HTTP profile or the ONECONNECT profile. I was considering disabling the ONECONNECT profile, I just had not ever had an issue with ONECONNECT and http traffic in general, but I did see a technote where Pipelining and ONECONNECT are not compatible. I was unsure if the best option was to disable ONECONNECT or to disable Pipelining.