What platform? I wouldn't do it, anyway. Machines are cheap these days... If anything, people buy more cheap machines for webservers and split the load.
I don't know what workflow has to do with it but you have plenty of other reasons not to do it. Among other things (let's say memory, different needs for fixes on the OS patches), you need to cleanup some port conflicts, if you decide to do it.
jas.ini for example contains serviceNameConnect serviceNameListen for [JDENET] even though there is no reason for the JAS server to listen on the JDENET port. However, theoretically, your JAS server can start before your jde servicices and lock the 6013 (or whatever release you are on...) port. Some of these stanzas are used by SAW, so if you put another port for Listen in JAS, SAW won't work right - SAR 7695175, etc.
You can definitely do it but you would buy yourself some headaches that may exceed the cost of a cheap box for WebSphere...