I don't understand the question. What do you mean "services for SMA"? SMA is a servlet that uses JMX API to communicate with the PRPC engine. When SMA runs inside the same JVM as PRPC, it uses "local JMX"; when SMA is on another node it has to be configured with the platform specific remote JMX facility.
I don't believe that Pega has written a mbean to start or stop the prweb application. There may be native application server JMX API's to start or stop an application running inside a JVM. Pega platform includes a "remote Mbean" SOAP service that lets AES send requests to use the same API's that SMA uses. Technically, the API is not pega-specific -- if there's a native STOP API, I guess it could be called from AES using the execRemoteMBean activity and connector. Naturally, once pega (prweb) stops, the service would not be available to restart the application.
There is no means to start and stop a JVM entirely from AES as shipped -- it has facilities or abilities to manage processes. In theory, if you had a management service and exposed an API service, you could enhance AES to make calls to that service.