With the process of adaptation and redefinition of Java Remote Method Invocation for J2ME (Java 2, Micro Edition) environments, a reduced version of the Remote Method Invocation (RMI) came up. In this reduced version, called RMIOP, some heavy features such as multiplexing facility or its capacity to go through firewalls offered by the wire protocol, called Java Remote Method Protocol (JRMP), have been eliminated. In the present article it is explored how the recovery of the multiplexing facilities of JRMP, rejected during the RMIOP definition, can be carried out maintaining the J2ME idiosyncrasy. The article begins showing how to extend the triad of subprotocols already defined (SingleOpProtocol, StreamProtocol and MultiplexProtocol) with a new one (MultiplexConnnectionLessProtocol) equipped with special facilities to multiplex connections. It gives support for fast and light connection connectionless virtual connections generation and recycling. The paper ends with an empirical evaluation of the proposed subprotocols together with the already existing ones, in terms of end-to-end response time and the size of the frames transmitted through the network, showing the goodness of the protocols.