Currently, the closure of the channel or connection is properly handled only when the awaitList in the Connection object is empty. In that case, the relevant frames are processed by the onFrameReceived function of either the channel or the connection. However, if such a frame reaches a frame handler on the awaitList, the global closure handling is ignored. As a result, the objects do not transition to their proper states, the closed channel is not removed from the client's channel list, and other necessary cleanup actions are not performed.

I propose that for two specific frame types: MethodConnectionCloseFrame and MethodChannelCloseFrame - we should invoke the appropriate onFrameReceived functions, even if the frame handler from the awaitList has already handled them.