Entity Framework DbContext Connection Output

Are you connecting to a custom assembly? If so, it's likely that something in that assembly or a library that it calls is writing to the debug output.

You can work around this in LINQPad by clearing the trace listeners:

Trace.Listeners.Clear();