You can also use Powershell v3 to list streams (maybe as a fallback for stream.exe), powershell always takes time to startup, so this is a bad choice for single calls. But if you were to write something script-based that needs to makes heavy use of streams, I'd choose this over the external tool approach, should be much easier and not much slower, once the powershell session is initialized and rushes through the filesystem.
powershell.exe -command gi .\<yourfilewithstreams.ext> -stream *And then there also is "dir" from cmd.exe, just to mention these alternatives! o)
dir <yourfilewithstreams.ext> /r