As you are running Solaris, install Sun Studio. The bundled dbx can help you figuring out if there is actually a leak and where it happens.

$ dbx /usr/bin/sleep
For information about new features see `help changes'
To remove this message, put `dbxenv suppress_startup_message 7.7' in your .dbxrc
Reading sleep
Reading ld.so.1
Reading libc.so.1
(dbx) check -leaks                                                           
leaks checking - ON
(dbx) run 10      
Running: sleep 10 
(process id 3032)
Reading rtcapihook.so
Reading libdl.so.1
Reading rtcaudit.so
Reading libmapmalloc.so.1
Reading libgen.so.1
Reading libm.so.2
Reading rtcboot.so
Reading librtc.so
RTC: Enabling Error Checking...
RTC: Running program...
Reading libshell.so.1
Reading libcmd.so.1
Reading libast.so.1
Reading fr_FR.UTF-8.so.3
Reading methods_unicode.so.3
Checking for memory leaks...

Actual leaks report    (actual leaks:            0  total size:          0 bytes)

Possible leaks report  (possible leaks:          0  total size:          0 bytes)

execution completed, exit code is 0

The command you are searching for is probably 'sar' this is usually not pre installed.. In opensuse it comes with the package sysstat.. google fot it to find and use..

Sar is always installed with Solaris but it cannot help pinpointing what specific process is using too much memory nor identifying a memory leak source.