It isn't supported out-of-the-box, you would need to create a custom trace listener by inherting from the CustomTraceListener class.
Regarding the connection pooling issues, I'm not sure what bug are you exactly referring to but it might more of a connection management-related problem since DAAB doesn't actually do the pooling but relies on ADO.NET to do that. Chris Tavares mentioned
a bug in 3.0 that was fixed in version 5.0 in this
Global Technologies and Solutions