WCF-NetNamedPipe Adapter Is Not Disposing of ChannelFactory by TheDavester

I have a WCF service, hosted in IIS 7.5 / WAS, that is exposed through an endpoint using the NetNamedPipe binding. I am sending to this service via a Solicit-Response send port using the WCF-NetNamedPipe adapter. This send port is not using SSO.

The trace log for this service rapidly accumulates "Throwing an exception" trace entries (http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.ThrowingException.aspx) in the root activity that are recording the following two exceptions:

System.ServiceModel.CommunicationException, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089

System.IO.PipeException, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089

With the message:
There was an error reading from the pipe: The pipe has been ended. (109, 0x6d).

It appears that the WCF adapter is not disposing of the channel factory that it is using and thus abruptly ending the pipe.