I would like to find out if this is a fluke that happened to me just
this once, or if others have had the pleasure, and I may have stepped on
a bug.

Last night I was grepping from CI, and locked up without getting any
output. So I broke out, and entered ABORT. This hung as well, so I broke
again, and shutdown Reflection. I restarted, logged back in, and
reissued my grep successfully, so I wasn't doing something normally
"illegal". Tonight, I noticed that my session was still showing, which
is especially odd since Ops knows to abort all sessions except the
console. ABORTJOB did me no good. Neither did NSCONTROL KILLSESS= nor
ABORTCON. MPEX's KILL didn't work, nor did the POSIX shell's kill, and
while I am not trying to start a thread on unabortable sessions, those
are pretty much all the ways I know to kill sessions.

So, has this happened to anyone else? Or should I switch to decaf and
sing hakuna matata (as if I would be here now and awake without
caffeine...).