Introduce a close method for memstore for release active segment

Per the analysis in parent issue, we will always have an active segment in memstore even if it is empty, so if we do not call close on it, it will lead to a netty leak warning message.

Although there is no real memory leak for this case, we'd better still fix it as it may hide other memory leak problem.