On iOS it does. Removing an app from the "recent apps list" 1. removes it from the list and 2. kills it if it was "alive" or suspended.
But because it's a "recent apps list", not a task switcher, most of the applications in the list are likely either already dead or suspended (frozen in memory with no CPU activity)
Now, I know Apples current method of working with background apps is correct (easiest for everyone). Apple does need to do something about it though. Google Latitude for example can 'run' (I'm not actually sure what code is executed, if any) even after being removed from the 'tray'. This all adds up to a pretty shitty experience for those who have no idea on how all this actually works, be it Apples fault or not.
Hence "likely".
> Google Latitude for example can 'run' (I'm not actually sure what code is executed, if any) even after being removed from the 'tray'.
That simply is not possible, once it's been removed from the switcher it can not be running unless it's the currently active application.
Furthermore location-aware applications are actually the easiest possible offenders to manage: they'll keep the location marker enabled in the status bar (although that can conflict with genuine users of the API such as Reminders) and they will appear with a purple arrow in Settings > Location Services.
It's fine for me, I can working it all out. But the average iPhone owner can't. You would be surprised at how many dont even know about removing the 'tasks'. All usage adds up especially with the limited resources on a phone.
on android before ICS there was no way to remove apps from the recent list, but you could shut down an app from the app management in settings.
i'm not sure if android 4's swiping apps away on the recent list "closes" them in a similar way to the android <= 3's app management "close app" button? anyone else able to verify?