Analyzing profiler data - why would event class 15 (audit logout) cause high reads ?

Im doing some performance checking on one of my systems and the top trace records by duration and reads are those with an event class of 15.  Why would simply closing the connection(s) cause such high read values - which implies a lot of i/o?