There could be server side traces created and run be the sp_trace_**** set of stored procedures. (I usually kick these sort of traces off from a scheduled job.)

You could run profiler to find the source. If it turns out to be from the server itself, search the sprocs/agent jobs for sp_trace