Is your setup allowing "Server Collaboration", i.e. the creation of Server Objects in the AccessPoint? If so, then a simple but badly written expression in a Server Object can run off with all ram and/or cpu cycles. And they may be difficult to spot.
If you think this could explain the behavior you are experiencing, try to determine when exactly the cpu goes haywire, and who is actively using a document in the AP at that point in time.